Motor vehicle operation information providing system

ABSTRACT

A data collection controller  4  to and from which a removable memory  12  can be attached and removed is mounted on a vehicle  1 , and is connected to a predetermined data storage  3 . In the data collection controller, driver codes, service route codes, and the like can be entered with code setting buttons  8  and  9 , while these code data and data in the predetermined data storage can be downloaded with a download button  7  into the removable memory. The downloading is performed every time the driving of the vehicle is completed. The removable memory is collected when a predetermined time period (for example, one month) has elapsed. Driving information for each driver and each service route is analyzed based on the data recorded in the collected removable memory.

TECHNICAL FIELD

The present invention relates to a driving information providing systemfor collecting and analyzing information about vehicle driving in orderto increase the efficiency of the driving.

BACKGROUND ART

For those who use vehicles as means of transportation for work, leisure,or the like, information to ensure efficient driving (for example,information about fuel costs) is useful. Particularly for transportcompanies and the like having many commercial vehicles, the efficiencyin driving, which will have impacts on costs and customer confidence, isa critical issue. The efficient driving means, for example, the drivingrequiring less fuel costs, causing no damage to the vehicle and goodsloaded, and no traffic accident.

To achieve such an efficient driving, driving information is collectedfrom vehicles after driving and analyzed for use in future driving.

FIG. 7 is a diagram showing a first example of a known drivinginformation providing system intended for such use as described above.Referring to FIG. 7, reference numeral 1 denotes a vehicle, referencenumeral 2 denotes a vehicle controller, reference numeral 3 denotes apredetermined data storage, reference numerals 20 and 21 denoteconnectors, reference numeral 22 denotes a cable, and reference numeral23 denotes a notebook computer.

The vehicle controller 2 is a controller for controlling the driving ofthe vehicle 1. Together with various detection signals (for example,engine-revolution detection signals and vehicle-speed detection signals)from each part of the vehicle, operation signals from the driver (forexample, acceleration operation signals, brake operation signals, andgearshift operation signals) are inputted into the vehicle controller 2.Based on these signals, various control signals (for example,fuel-injection control signals and gearshift control signals) aregenerated and outputted from the vehicle controller 2 to each part ofthe vehicle.

The predetermined data storage 3 is a storage device for selecting, asappropriate, data that are assumed to be associated with efficientdriving (predetermined data) from data appearing in the vehiclecontroller 2, and recording the selected data. The connector 20 is aconnector connected to the predetermined data storage 3.

Data (driving information) stored in the predetermined data storage 3 iscollected as described below. That is, a staff member at an intermediaryagent (for example, a vehicle dealer) for a data analysis center bringsthe notebook computer 23 to the vehicle 1, inserts the connector 21 forthe cable 22 into the connector 20 for the vehicle to make connectionwith the predetermined data storage 3, extracts the data therefrom intothe notebook computer 23, thereby collecting the data.

The staff member then brings the notebook computer 23 back to theintermediary agent, sends the collected data to the data analysiscenter, thereby having the driving information analyzed by the center.

In a second example of a known driving information providing system,removable memory cards prepared for each driver are collected to analyzedriving information.

In this case, a driver inserts his/her own memory card into apredetermined vehicle-mounted unit at the beginning of vehicle drivingto record data during the driving. On completion of the driving, thedriver pulls out the memory card, inserts the memory card into adedicated computer in a service office, such as a garage, to have thedata read and analyzed by the computer.

A first problem with the first known example described above is that thecollection of driving information requires time and effort, and a secondproblem is that driving information for each driver cannot be obtained.

A problem with the second known example described above is an increasedcost, since a dedicated device for preparing a memory card for eachdriver and reading the memory card needs to be set up in each serviceoffice.

The first problem with the first known example will now be described. Inthis example, a staff member for collection goes to each vehicle andconnects a notebook computer thereto for collecting data. Sincededicated personnel are required and it takes as long as 20 to 30minutes per vehicle, time and effort are involved in collecting data.

The second problem with the first known example will now be described.Drivers of the same vehicle may vary from day to day, or may changeduring a single day. However, while driving information for each vehiclecan be obtained, driving information for each driver cannot be obtained.Although transport companies and others often request for the analysisof driving information for each driver so that individual evaluation andinstruction can be made, this example cannot meet such a request.

Finally, the problem with the second known example will be described.The dedicated device for writing and reading to and from a memory cardfor each driver is relatively expensive (for example, several hundredsof thousands of yen per device). Since the cost of installation at eachservice office and the cost of appropriate maintenance after theinstallation are required, the dedicated device in the second knownexample is considerably expensive.

The present invention aims to solve the problems described above.

DISCLOSURE OF INVENTION

An object of the present invention is to reduce the time and effortrequired for collecting driving information from vehicles after driving.

A further object of the present invention is to obtain driverinformation, service route information, and the like, as well as vehicledata, in collecting driving information from vehicles after driving.

A still further object of the present invention is to reduce the costsof collecting and analyzing driving information from vehicles afterdriving.

To achieve these objects, in a driving information providing systemincluding a predetermined data storage for storing predetermined datafrom data appearing in a vehicle controller, wherein data is extractedfrom the predetermined data storage for the analysis of drivinginformation, the driving information providing system of the presentinvention further includes a data collection controller connected to thepredetermined data storage; and a removable memory that can be attachedto and removed from the data collection controller. The data collectioncontroller includes at least a code entry section for entering desireddata in code; and a download section for downloading data entered incode and data in the predetermined data storage into the removablememory currently attached. The removable memory in which data isdownloaded is collected and provided for the analysis of drivinginformation.

In the predetermined data storage described above, data can be stored bya storage-saving-type data recording method. An example is afrequency-accumulation-type data recording method in which every time adata value detected at predetermined intervals falls within apredetermined range of data values, a detection count for the range isaccumulated and recorded.

The above-described data to be entered in code is a plurality of data.For example, at least two of driver data, service route data, senderdata, goods data, loading ratio data, and data for driving time periodscan be entered in code (Note: loading ratio=(actual load)/(rated load)).

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows the main part of a vehicle in the driving informationproviding system according to the present invention.

FIG. 2 is a diagram for explaining an example of a storage-saving-typedata recording method.

FIG. 3 is a diagram for explaining the flow of data analysis accordingto the driving information providing system of the present invention.

FIG. 4 shows examples of code settings.

FIG. 5 is a diagram for explaining the implementation of the presentinvention.

FIG. 6 illustrates the conditions of data downloaded to a removablememory.

FIG. 7 is a diagram showing a first example of a known drivinginformation providing system.

BEST MODE FOR CARRYING OUT THE INVENTION

Embodiments of the present invention will now be described in detailbased on the drawings.

FIG. 1 shows the main part of a vehicle in the driving informationproviding system according to the present invention. Reference numeralscorrespond to those in FIG. 7. Reference numeral 4 denotes a datacollection controller, reference numerals 5 and 6 denote codeindicators, reference numeral 7 denotes a download button, referencenumerals 8 and 9 denote code setting buttons, reference numeral 10denotes a clock, reference numeral 11 denotes a quick setting buttonassembly, and reference numeral 12 denotes a removable memory. Referencenumerals identical to those in FIG. 7 represent the same components. Theclock 10 provides the current time.

First, an overview will be given. In the present invention, the vehicle1 is provided with the data collection controller 4, which is connectedto the predetermined data storage 3. The removable memory 12 can beattached to and removed from the data collection controller 4.

The data collection controller 4 has not only a function of addingdriver information and service route information, but also a function ofallowing these pieces of information and data stored in thepredetermined data storage 3 to be downloaded to the removable memory12.

Thus, when the removable memory 12 is pulled out and collected, drivinginformation to which driver information and service route informationare added can be collected. The detailed description will be givenbelow.

The code setting button 8 is a button for setting code numbers ofdrivers, while the code indicator 5 is an indicator for displaying thecode numbers set.

The code setting button 9 is a button for setting code numbers ofservice routes, while the code indicator 6 is an indicator fordisplaying the code numbers set.

At each press of the code setting button 8 and 9, code numbers areincremented, for example, from 0, 1, 2, to 3.

FIG. 4 shows examples of code settings. FIG. 4(1) shows an example ofservice route code settings. For example, code number “0” is assigned tothe service route “Tokyo-Nagoya”, while code number “1” is assigned tothe service route “Nagoya-Matsumoto”.

FIG. 4(2) shows an example of driver code settings. For example, codenumber “0” is assigned to the driver “Tanaka”, while code number “1” isassigned to the driver “Hayakawa”.

The quick setting button assembly 11 is equivalent to abbreviateddialing buttons of a phone, and allows code settings of a specificcombination to be made with a single press of a button.

For example, if the driver Hayakawa often drives the vehicle 1 on theservice route Matsumoto-Niigata, the combination of specific codes, thatis, the driver=1 (Hayakawa) and the service route=2 (Matsumoto-Niigata)are stored in a button P₁ of the quick setting button assembly 11. Thus,code settings can be made with a single press of the button P₁, whilemany button presses are required for settings using the code settingbuttons 8 and 9. Although three buttons P₁ to P₃ are included in thequick setting button assembly 11 in FIG. 1, the number of buttons may bemore than that.

The code indicators 5 and 6, the code setting buttons 8 and 9, and acircuit (which is not shown since being a known circuit or being easilyconfigured by those skilled in the art) operating in response to themconstitute a code entry section.

In the example described above, the driver information and the serviceroute information are examples of information to be set in code.However, the information for code settings is not limited to them. Theymay be changed, or other information may be added to them, depending onthe perspective from which one desires to analyze the drivinginformation.

For example, the entry of the driver information is mandatory, while theservice route information may be replaced with sender information,loading ratio information, or information about driving time periods.Alternatively, three kinds of information, that is, the driverinformation, the service route information, and the sender informationmay all be entered (If one would like to increase the number ofinformation to be entered by codes, the numbers of the code settingbuttons and code indicators need to be increased, accordingly).

The download button 7 is a button for downloading the data stored in thepredetermined data storage 3 into the removable memory 12. The data isdownloaded with the addition of information corresponding to the codesset (information about a driver and service route) and clock information(downloading time) provided by the clock 10. The download button 7 and acircuit (which is not shown since being a known circuit or being easilyconfigured by those skilled in the art) operating in response to thedownload button 7 constitute a download section.

In the present invention, a data recording method in the predetermineddata storage 3 is a method for recording a large amount of data in asmall storage, in other words, a recording method that can be referredto as a storage-saving-type data recording method.

FIG. 2 is a diagram for explaining an example of such astorage-saving-type data recording method. This is a diagram forexplaining, in a way easy to understand, how to record vehicle speeddata.

The horizontal axis indicates vehicle speeds and the vertical axisindicates detection counts (cumulative counts). The vehicle speedsranging from low to high levels are divided at a predetermined speedinterval of ΔV (for example, 5 km/h) into many vehicle speed ranges. InFIG. 2, each of the intervals between V₂ and V₃, and between V_(N+1) andV_(N+2) is ΔV.

The vehicle speed is detected at every predetermined time interval (atevery Δt), and the detection count of the vehicle speed range withinwhich the detected vehicle speed falls is accumulated. For example, whenthe detection count of the vehicle speed range V₂-V₃ is T₃, and then thevehicle speed subsequently detected (in Δt seconds) falls within therange of V₂-V₃, the detection count of the vehicle speed range increasesto T₃+1 by the addition of one.

All that is required for such recording is, for example, to providecounters corresponding to each of vehicle speed ranges, in thepredetermined data storage 3. When a vehicle speed is detected, acounter corresponding to the vehicle speed range within which thedetected vehicle speed falls is incremented by one. Since only a storagecapacity for the counters is required, the required storage capacity issignificantly reduced compared to the case where a detected vehiclevalue itself is recorded each time. (Since counter value 1 is assumed tobe equivalent to Δt seconds in terms of time, an approximate cumulativetime of travel in the vehicle speed range can be determined bymultiplying the counter value by Δt seconds).

Such a recording method can be referred to as afrequency-accumulation-type data recording method since the number oftimes a certain vehicle speed range is detected, in other words, thefrequency of appearance of certain data is accumulated and recorded.

There are various types of storage-saving-type data recording methodsother than the frequency-accumulation-type data recording method. Forexample, the storage capacity can be saved by recording data that iscompressed through the use of a compression technique.

FIG. 5 is a diagram for explaining the implementation of the presentinvention. The driving of a vehicle from the insertion (at time point t₀on the left) to the removal (at time point t₅ on the right) of theremovable memory 12 is illustrated. The details will be described belowin the order of time.

(1) Time point t₀ . . . The driver Tanaka gets into the vehicle andinserts the removable memory 12 into the data collection controller 4 inFIG. 1. There is no need for pressing the download button 7 at thispoint. If the download button 7 is pressed from habit at the time ofgetting into the vehicle, data present in the predetermined data storage3 at this point is downloaded into the removable memory 12.

This poses no problem since the downloaded data is the same as thatpreviously being downloaded to the removable memory 12, that is, sincethis is simply redundant storing of the same data (for convenience ofexplanation in FIG. 5, data is assumed to be empty at time point t₀).

Then the driver Tanaka enters his/her own driver code (0) and the code(0) for the service route “Tokyo-Nagoya” to drive (thus the input codeis “00”).

(2) Time point t₁ . . . Upon arrival in the destination Nagoya, thedriver Tanaka gets out of the vehicle (without doing anything to operatethe data collection controller 4). The next driver Hayakawa subsequentlygetting into the vehicle and presses the download button 7. This allowsdata (D₀₁) recorded in the predetermined data storage 3 at this point tobe downloaded into the removable memory 12 (in this case, information,such as a driver code, service route code, and time, is added to bedownloaded).

Moreover, the driver Hayakawa enters his/her own driver code (1) and thecode (1) for the service route “Nagoya-Matsumoto” to drive (thus theinput code is “11”).

(3) Time point t₂ . . . Upon arrival in the destination Matsumoto, thedriver Hayakawa can get out of the vehicle without doing anything, ifnot scheduled to continue driving. However, in this example, the driverHayakawa is scheduled to subsequently drive the next service route“Matsumoto-Niigata”. To start the next driving, the driver Hayakawapresses the download button 7 to allow data (D₀₂) in the predetermineddata storage 3 to be downloaded into the removable memory 12, whileentering his/her own driver code (1) and the code (2) for the serviceroute “Matsumoto-Niigata” to drive (thus the input code is “21”).

(Drivers who subsequently get into the vehicle perform the sameoperation to the data collection controller 4).

(4) Time point t₄ . . . To start the next driving, the driver Yamamotowho has got into the vehicle in Niigata presses the download button 7 todownload data (D₀₄) in the predetermined data storage 3 into theremovable memory 12, while entering his/her own driver code (2) and thecode (3) for the service route “Niigata-Tokyo” to drive (thus the inputcode is “32”).

If the driver Yamamoto arrives in the destination Tokyo (time point t₅)at the time to collect the removable memory 12 (for example, when onemonth has elapsed since the insertion of the removable memory 12, or atthe end of month), the driver Yamamoto performs the operation forcollection, such as those described in 1 and 2 below.

1. Press the download button 7 (to download data (D₀₅) in thepredetermined data storage 3 into the removable memory 12).

2. Remove the removable memory 12.

The driver Yamamoto hands in the removed removable memory 12 to aservice office (see a service office 14 in FIG. 3 to be describedbelow).

FIG. 6 illustrates the conditions of data downloaded to the removablememory. Reference numeral 15 denotes a t₁ data file, reference numeral16 denotes a t₂ data file, reference numeral 17 denotes a t₃ data file,and reference numeral 18 denotes increments from the previous time.

The data (D₀₁) in the predetermined data storage 3 downloaded at thetime point t₁ shown in FIG. 5 is stored into the removable memory 12 inthe form of a single file, which is the t₁ data file 15. The data D₀₁contains many items, such as vehicle speeds and engine revolutions, thatare recorded in the manner shown in FIG. 2.

The data (D₀₂) in the predetermined data storage 3 downloaded at thetime point t₂ shown in FIG. 5 contains basically the same items. Adifference is that the data detected during the period from the timepoints t₁ to t₂ is added to the data (D₀₁) at the time point t₁. Thiscorresponds to the increments 18 from the previous time shown in FIG. 6.

The data detected during the period from the time points t₁ to t₂(corresponding to data D₁₂ in FIG. 5, that is, the data for the driverHayakawa driving the service route Nagoya-Matsumoto) can be determinedby D₀₂−D₀₁ (D₀₂−D₀₁=D₁₂).

FIG. 3 is a diagram for explaining the route of data analysis accordingto the driving information providing system of the present invention.Reference numerals correspond to those in FIG. 1. Reference numeral 13denotes a driver, reference numeral 14 denotes a service office,reference numerals A₁ to A₃ denote transport companies, referencenumerals B₁ to B₃ denote intermediary agents, and reference numeral Cdenotes a data analysis center. The transport companies A₁ to A₃ areshown as examples of customers.

In the transport companies A₁ to A₃, the removable memory 12 isperiodically (for example, once a month) collected from each vehicle 1.The removable memories 12 are collected at the service office 14 andsent to the intermediary agents B₁ to B₃ (or may be directly sent to thedata analysis center C).

For data analysis of driving information, the intermediary agents B₁ toB₃ mediate between the transport companies A₁ to A₃, which arecustomers, and the data analysis center C. For example, dealers thathave sold vehicles to the transport companies A₁ to A₃ also serve assuch intermediary agents.

The data analysis center C analyzes driving information sent via theintermediary agents B₁ to B₃, or directly from the transport companiesA₁ to A₃. The driving information from the intermediary agents B₁ to B₃may be transmitted to the data analysis center C by the method of datatransfer.

The results to be obtained by the analysis obviously depend on the typeof data downloaded to the removable memory 12. Examples of the resultsare shown below.

For each vehicle, the results to be obtained include cost data (such asthe amount of fuel consumption, fuel costs, and travel distances),environmental data (such as the amount of emissions of CO₂, NO_(x), andPM), and driving time ratio (the ratio of driving time to idling time).

As for each driver, the results to be obtained include fuel costs,driving time, travel distances, the frequency and time of use of enginebraking, the use of a foot brake (such as the frequency of hardbraking), the number of engine revolutions in upshifting, cruisingspeeds, which gear is most frequently used during driving at what speed,and the frequency of hard acceleration.

As shown in FIG. 1, signals (data) appearing in the vehicle controller 2can be downloaded into the removable memory 12 as much as required.Therefore, necessary data can be downloaded if specific analyses arerequired.

The analyses are sent back along the same route, which the drivinginformation has been sent, in reverse order. When the analyses arereceived, the transport companies A₁ to A₃ can give proper guidance toeach driver while calculating costs for each service route and eachsender, based on detailed data obtained on each driver and each serviceroute.

For example, specific guidance, such as to reduce hard braking or toreduce vehicle speed, can be given to a driver who frequently applieshard braking.

As for cost calculation for each service route, for example, the needfor some level of price increase is considered for a route with manyuphills, which cause large fuel consumption; and the change of startingtime is considered, for cost reduction, for a route in which drivingtime varies greatly depending on the time of day (due to trafficcongestion and so on).

Moreover, if codes for the types of goods loaded, senders, and the likeare entered in the data collection controller 4, a detailed costcalculation for each goods loaded (or each sender) can be made. In thiscase, transportation charges can be changed depending on the goodsloaded even if carried in the same service route.

As described above, in the driving information providing system of thepresent invention, time and effort required for collecting drivinginformation can be reduced since it is done simply by collecting thesmall removable memories 12.

Data from the predetermined data storage 3 only allows for the analysisof vehicle data. However, since desired data can be added by code entry,analysis from new perspectives, such as the analysis for each desireddata, can be made.

Moreover, the use of the storage-saving-type data recording method (forexample, frequency-accumulation-type data recording method) in thepredetermined data storage 3 allows a larger amount of data (that is,data for long periods of time) to be stored in a small-capacity storage.

When a plurality of data codes are entered, driving information can beanalyzed from the corresponding number of perspectives. For example,when codes of driver data and service route data are entered, drivinginformation can be analyzed from perspectives, such as for each driver,each service route, and each combination of them.

1. A driving information providing system for collecting data for theanalysis of driving information about a vehicle driven by an operator,comprising: a vehicle controller that receives detection signalscarrying information about vehicle operation and operating signals fromthe operator, the vehicle controller generating control signals forcontrolling the vehicle; a predetermined data storage for storingpredetermined data selected from data appearing in the vehiclecontroller; a removable memory; and a data collection controller thatreceives the predetermined data from the predetermined data storage, thedata collection controller including at least a code entry section forentering desired data in code, and a download section having a downloadbutton for downloading data entered in code and data in thepredetermined data storage into the removable memory when the downloadbutton is actuated, the removable memory being connectable to anddetachable from the data collection controller, wherein the removablememory in which data is downloaded is collected and provided for theanalysis of driving information, and wherein the data that is entered incode in the code entry section includes a driver code that distinguishesthe operator of the vehicle from other vehicle operators.
 2. The drivinginformation providing system according to claim 1, wherein data isstored in the predetermined data storage by a storage-saving-type datarecording method.
 3. The driving information providing system accordingto claim 2, wherein a frequency-accumulation-type data recording methodis adopted as the storage-saving-type data recording method, thefrequency-accumulation-type data recording method being a method inwhich every time a data value detected at predetermined intervals fallswithin a predetermined range of data values, a detection count for therange is accumulated and recorded.
 4. The driving information providingsystem according to claim 1, wherein a plurality of data is entered incode.
 5. The driving information providing system according to claim 4,wherein data to be entered in code is at least two of driver data,service route data, sender data, goods data, loading ratio data, anddata for driving time periods.
 6. The driving information providingsystem according to claim 2, wherein a plurality of data is entered incode.
 7. The driving information providing system according to claim 3,wherein a plurality of data is entered in code.
 8. The drivinginformation providing system according to claim 6, wherein data to beentered in code is at least two of driver data, service route data,sender data, goods data, loading ratio data, and data for driving timeperiods.
 9. The driving information providing system according to claim7, wherein data to be entered in code is at least two of driver data,service route data, sender data, goods data, loading ratio data, anddata for driving time periods.
 10. The driving information providingsystem according to claim 1, wherein the data entered in code includesdata identifying different drivers.
 11. The driving informationproviding system according to claim 1, wherein data pertaining to agiven parameter of vehicle operation is stored in the predetermined datastorage by a frequency-accumulation-type data recording method, in whichpossible values for the given parameter are divided into ranges, actualvalues for the given parameter are detected at predetermined timeintervals, and every time an actual value that lies within one of theranges is detected, a count value corresponding to said one of theranges is incremented.
 12. The driving information providing systemaccording to the claim 1, wherein the detection signals received by thevehicle controller include engine-revolution detection signals andvehicle-speed detection signals.
 13. The driving information providingsystem according to claim 12, wherein a vehicle operating signalsreceived by the vehicle controller include at least one of accelerationoperating signals, brake operating signals, and gear shift operationsignals.
 14. The driving information providing system according to claim1, wherein the operating signals received by the vehicle controllerinclude at least one of acceleration operation signals, brake operationsignals, and gear shift operation signals.
 15. The driving informationproviding system according to claim 1, wherein the operating signalsreceived from the vehicle controller include acceleration operationsignals, brake operation signals, and gearshift operation signals. 16.The driving information providing system of claim 1, wherein the codeentry section comprises at least one manually operable button forentering the desired data in code.
 17. A driving information providingsystem for collecting data for the analysis of driving information abouta vehicle driven by an operator, the vehicle having a vehicle controllerthat receives detection signals carrying information about vehicleoperation and operating signals from the operator, the vehiclecontroller generating control signals for controlling the vehicle, saiddriving information providing system comprising: a predetermined datastorage for storing predetermined data selected from data appearing inthe vehicle controller; a removable memory; and a data collectioncontroller that receives the predetermined data from the predetermineddata storage, the data collection controller including at least a codeentry section for entering desired data in code, and a download sectionhaving a download button for downloading data entered in code and datain the predetermined data storage into the removable memory when thedownload button is actuated, the removable memory being connectable toand detachable from the data collection controller, wherein theremovable memory in which data is downloaded is collected and providedfor the analysis of driving information, and wherein the desired datathat is entered in code in the code entry section includes a driver codethat distinguishes the operator of the vehicle from other vehicleoperators.